CRD cleanup + helm client download retires + error classification#6291
CRD cleanup + helm client download retires + error classification#6291zhoxing-ms merged 116 commits intoAzure:mainfrom
Conversation
modified: src/connectedk8s/azext_connectedk8s/_params.py modified: src/connectedk8s/azext_connectedk8s/_utils.py modified: src/connectedk8s/azext_connectedk8s/custom.py new file: src/connectedk8s/azext_connectedk8s/patch-file.yaml
modified: src/connectedk8s/azext_connectedk8s/_utils.py modified: src/connectedk8s/azext_connectedk8s/custom.py
modified: src/connectedk8s/azext_connectedk8s/custom.py
modified: src/connectedk8s/azext_connectedk8s/commands.py modified: src/connectedk8s/azext_connectedk8s/custom.py new file: src/connectedk8s/azext_connectedk8s/tests/latest/recordings/test_forcedelete.yaml modified: src/connectedk8s/azext_connectedk8s/tests/latest/test_connectedk8s_scenario.py
modified: src/connectedk8s/azext_connectedk8s/custom.py renamed: src/connectedk8s/azext_connectedk8s/patch-file.yaml -> src/connectedk8s/azext_connectedk8s/remove_crd_finalizer.yaml modified: src/connectedk8s/azext_connectedk8s/tests/latest/recordings/test_forcedelete.yaml modified: src/connectedk8s/azext_connectedk8s/tests/latest/test_connectedk8s_scenario.py
modified: src/connectedk8s/azext_connectedk8s/tests/latest/test_connectedk8s_scenario.py
modified: src/connectedk8s/azext_connectedk8s/custom.py
modified: src/connectedk8s/setup.py
modified: src/connectedk8s/azext_connectedk8s/tests/latest/recordings/test_forcedelete.yaml
modified: src/connectedk8s/azext_connectedk8s/tests/latest/recordings/test_forcedelete.yaml
….com/rohan-dassani/azure-cli-extensions into timeout_in_crd_deletion_force_delete
modified: src/connectedk8s/azext_connectedk8s/tests/latest/recordings/test_forcedelete.yaml
modified: src/connectedk8s/setup.py
|
Hi @rohan-dassani, |
|
Hi @rohan-dassani, |
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
modified: src/connectedk8s/setup.py
modified: src/connectedk8s/azext_connectedk8s/_utils.py
modified: src/connectedk8s/azext_connectedk8s/_constants.py modified: src/connectedk8s/azext_connectedk8s/_utils.py
modified: src/connectedk8s/azext_connectedk8s/custom.py
| @@ -212,6 +212,9 @@ | |||
| Cluster_Diagnostic_Checks_Job_Log_Save_Failed = 'Failed to save cluster diagnostic checks job log' | |||
| # Diagnostic Results Name | |||
| Outbound_Connectivity_Check_Result_String = "Outbound Network Connectivity Result:" | |||
There was a problem hiding this comment.
I think this is a little confusing. Let's name the tests as "Outbound_Connectivity_Check_For_Onboarding" and "Outbound_Connectivity_Check_For_ClusterConnect" at all places to make it clear in the code as well
There was a problem hiding this comment.
Same comment for logs as well which we're appending in the arc_diagnostic_logs folder
There was a problem hiding this comment.
Yeah but OBO is not the only endpoint for cluster connect right , so if any other endpoint required for cluster connect fails then the log will not give the right impression to us and to the user.
| # Validating if outbound connectiivty is working or not and displaying proper result | ||
| if(outbound_connectivity_response != "000"): | ||
| # since connectivity to obo endpoint is required only for cluster connect feature , we only give out a warning if connectivity to obo endpoint is not present | ||
| if obo_check_response_code == "000": |
There was a problem hiding this comment.
Can't we have this condition outside of the parent if check? That way we keep it independent and will be easy to increase the list of endpoints in each category easily in future
There was a problem hiding this comment.
The reason for keeping this inside the if condition was , that supposing that the outbound connectivity isnt there to any endpoint , it will still give out the warning about obo endpoint and then it will say outbound connectivity fail when it checks the mcr endpoint.
So i thought if mcr itself fails , then pointing to obo specifically doesnt make sense and the user should look into all the endpoint network requirements document. And if mcr connectivity is there than pointing out if some specific endpoint is not listed makes more sense.
modified: src/connectedk8s/azext_connectedk8s/_precheckutils.py modified: src/connectedk8s/azext_connectedk8s/_utils.py
modified: src/connectedk8s/azext_connectedk8s/_utils.py
|
[Release] Update index.json for extension [ connectedk8s ] : https://dev.azure.com/azclitools/internal/_build/results?buildId=57185&view=results |
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally?For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.jsonautomatically.You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify
src/index.json.